Are you interested in contributing to the Books project?

Books is entirely a volunteer effort and more volunteers only make the application better.

Do you like writing code?
If you're a programmer, there are two main ways that you can contribute to Books development. The core program is written entirely in Objective-C using Apple's Cocoa framework. If you're comfortable writing object-oriented Obj-C code and enjoy working in Xcode and have some ideas that you'd like to implement, drop us a line.

If you're not a Cocoa programmer, but do develop in other languages, you may want to take a look at developing Books plugins. We are happy to provide the necessary wrappers for your Java, Python, Ruby, and <insert language here> code. Most of the plugins are written in languages other than Objective-C. Again, drop us a line for more details.

Are you a designer?
If you're a designer, we are always looking for help with new icons and display plugins. If this might interest you, drop us a line.

Do you speak another language?
Books has been translated into several languages purely through the efforts of dedicated volunteers. Enrico Richter manages the Books translations, so contact him if you would like to contribute a translation.

Are you just a regular user who wants to help out?
If you don't code, design, or translate, we can still use your help. Books is only as good as the feedback we receive. We like getting bug reports and feature suggestions. If you find a problem with Books, please report it so that we can fix it. If you have an idea for a great feature that Books is missing, please let us know.

Likewise, you can help us by getting the word out about Books. You can do this by mentioning it in conversation (when relevant, of course), posting a link to your blog or journal, or writing some feedback at any number of the Mac software review sites. (iusethis, MacUpdate, and VersionTracker are popular ones.)

Did You Know?

Typical refinements to the Books interface have been products of this process: A user tells us that some aspect of the interface could be better by doing X or doing what another app does. The developer scrambles to learn how to do this, and implements the tweak in his local build. He sends the changes to a handful of trusted testers and gets their feedback. If the feedback is positive, the change usually shows up in the next release.